Silk Road forums
Discussion => Silk Road discussion => Topic started by: AnonymousAddict on January 05, 2013, 03:20 pm
-
Iv downloaded it and the Icon says MIRC chat... i WENT to the sticky thread and it wasnt much help really.. Could someone be nice enuff and tell me if iv downloaded the wrong thing, ill show u think link i found it
http://clsvtzwzdgzkjda7.onion/viewtopic.php?f=7&t=1458 i went here and then highlighted and went to the clearnet site whch was **warning clearnet** http://www.irchelp.org/irchelp/irctutorial.html
So is that the wrong oone? iv never really payed much attention to the live chat.. so if someone could help me get to it id be greatfull
-
Are you trying to access the Silk Road chat?
Click the onion icon -> Settings -> Advanced, and uncheck "Configure ControlPort automatically", then restart the browser bundle. That will force the SocksPort to be 9050, otherwise a random one is selected.
In mIRC, create a new entry for an IRC network. Call it "Silk Road" I guess.
Enter this as the server: silcroadg3c3mtu6.onion
Enter this as the port: 6667
Select SOCKS5 proxy
Enter this as the proxy address: 127.0.0.1
If you are using the standalone Tor client
Enter this as the proxy port: 9050
If you are using the browser bundle
Enter this as the proxy port: 9150
Fill out the info for username and all that.
Connect.
Edit: Changed info about SocksPort
-
u still cant seem to get it to connect,,, not sure what im doing what.
-
What error does it give you?
-
Click the onion icon -> Settings -> Advanced, and uncheck "Configure ControlPort automatically", then restart the browser bundle. That will force the SocksPort to be 9050, otherwise a random one is selected.
In mIRC, create a new entry for an IRC network. Call it "Silk Road" I guess.
Enter this as the server: silcroadg3c3mtu6.onion
Enter this as the port: 6667
Select SOCKS5 proxy
Enter this as the proxy address: 127.0.0.1
Enter this as the proxy port; 9050
Fill out the info for username and all that.
Connect.
In my Vidalia Control Panel Settings the TCP connection is set to 9151 and thats what i used in MIRC.
Is this why i get this error:
* Connect retry #7 silcroadg3c3mtu6.onion (6667)
-
* Unable to resolve server
-
Yeah, that's wrong. You want it to be 9150, not 9151. 9151 is the control port, not the Tor proxy port. Confusing, I know.
It used to be 9050. It changed last update.
-
Screw IRC... my TorChat doesn't work anymore, and I've reinstalled it twice!! WTF!
-
Um... huh? I like your posts Sleepy: I'm happy to help you. But can you explain what you mean? The actual stand alone TorChat has ceased functioning, or the Pidgin plugin has?
-
Changed it to 9150 in MIRC but still no luck.
Its hard to provide any additional infos but i will try:
I made a fresh portable install on the same USB stick Tor Browser Bundle is running from.
That particular instance of MIRC is enabled in the firewall.
Connecting to clearnet networks works without problems(with my IP though).
Followed the above steps meticulously.
For clarification: The port in my Vidalia Control Panel Settings is set to 9151 and to 9150 in MIRC and Firefox.
Is that correct?
Anyway still get the increasingly annoying:
* Connecting to silcroadg3c3mtu6.onion (6667)
-
* Unable to resolve server
-
* Connect retry #1 silcroadg3c3mtu6.onion (6667)
-
* Unable to resolve server
-
* Connect retry #2 silcroadg3c3mtu6.onion (6667)
-
* Unable to resolve server
................................
Any ideas?
-
In my Vidalia Control Panel Settings the TCP connection is set to 9151 and thats what i used in MIRC.
Is this why i get this error:
* Connect retry #7 silcroadg3c3mtu6.onion (6667)
-
* Unable to resolve server
9151 is the ControlPort, not the SocksPort. The SocksPort is still 9150.
Unable to resolve server is a DNS resolving error.
There is a way around this using Tor's mapaddress functionality.
Shut down TBB.
Open the Tor configuration file with a text editor. On Windows, it should be in Data\Tor\torrc, wherever you extracted your browser bundle.
Add this to the end of torrc:
mapaddress 192.0.2.2 silcroadg3c3mtu6.onion
Start the browser bundle.
Go to mIRC and enter 192.0.2.2 for server instead of the onion address.
Edit: Port 9150, not 9050
-
Thx for the help astor!
The end of my torrc file looks like this now:
SocksListenAddress 127.0.0.1
SocksPort 9150
ControlPort 9151
mapaddress 192.0.2.2 silcroadg3c3mtu6.onion
But i still end up with error messages:
* Connect retry #2 192.0.2.2 (6667)
-
* Unable to connect to server (Connection timed out)
-
* Connect retry #3 192.0.2.2 (6667)
-
* Unable to connect to server (Connection timed out)
This is so frustrating i even did a fresh install of the bundle and mIRC earlier and followed the steps to the point.
Im on win7pro btw and the only difference to a fresh install is my firewall control(where this instance of mirc is whitelisted).
-
Er... not to contradict you and your wisdom, astor, but it did change to 9150. I swear it did in 2.3.25-4. Perhaps yours is still on 9050 because (like me) you set it that way through the standard torrc file? The browser bundle is now on 9150 in both Windows and Linux statically. It doesn't vary anymore.
It looks like you've got the info right, anonymouse, but that you just don't have a circuit to the server yet. Try getting a new identity every few minutes and just don't hold your breath waiting. Should work. If you aren't on in 15 minutes, I'm wrong and it's probably something else that's the problem.
P.S. - I hate mIRC. Not for particularly good reasons, but I still do. Try xchat. Or even pidgin.
-
It occurs to me -- you shouldn't need mIRC whitelisted. mIRC is only connecting to your local computer (that's what happens when you set things to go through Tor -- they connect to it on your local computer, and then Tor makes the actual connections to the internet).
So it should *at least* be saying it was able to connect to 127.0.0.1:6667. Astor, are you sure that map thing doesn't actually alter the Windows hosts entries and cause mIRC to think it has the address and try to connect to it w/o a lookup or proxy...?
Just a stab in the dark.
-
So it said Unable to resolve server before, and now it says Unable to connect to server (Connection timed out).
The SocksPort in your torrc is 9150. Are you sure it is 9150 in mIRC?
I screwed up earlier when I said 9050 because I forgot it's different in TBB than in the standalone Tor client.
Make sure it is set to 9150. Another question, do you get that error immediately or does it take 10-30 seconds to see it?
-
It occurs to me -- you shouldn't need mIRC whitelisted. mIRC is only connecting to your local computer (that's what happens when you set things to go through Tor -- they connect to it on your local computer, and then Tor makes the actual connections to the internet).
So it should *at least* be saying it was able to connect to 127.0.0.1:6667. Astor, are you sure that map thing doesn't actually alter the Windows hosts entries and cause mIRC to think it has the address and try to connect to it w/o a lookup or proxy...?
Just a stab in the dark.
The only thing mapaddress does is translate an IP address into an onion domain. It's useful when programs don't know how to handle pseudo-TLDs and stuff. So the IRC client knows what an IP address is, it sends it to Tor's socks port, and Tor translates it to the onion domain and does what it normally does to connect to hidden services.
-
I been timing out the last 24 hours...sometimes you just cant get a connection...;)
They are just talking about the same thing they did last Tuesday night...who's hash taste like ginger pubes, which rc analog is closest to mescaline and btc rate ceiling.
X)
nomad
-
That's why I asked how long it takes to see the error. If they're getting the error immediately, they probably configured the wrong SocksPort. If it takes 10-30 seconds, they probably just can't reach the server.
-
I see your point, but... well what's confusing me is exactly what's reporting to mIRC that this silcroadxxx.onion address is 192.x.x.x?
It can't be Tor. Tor shouldn't have any more control than mIRC does over the system. Unless you're running it as admin in Windows? Does it require that?
So mIRC makes a function call to the operating system to resolve the human-readable URL into the 123.456.789.012 numeric form. It shouldn't be trying to resolve that itself, it needs to call the OS because if two people try to do the same job they['re going to do it slightly differently and then everything gets all fucked. So if it isn't Windows that's registering this address system-wide, and reporting that to mIRC when queried... which mIRC then uses to connect to 192.x.x.x... who is?
If that's the way it works, then it'll break mIRC. It'll always try to connect to a phantom 192 address that doesn't exist instead of 127.0.0.1:9150 the way it should. I just don't see how that mapaddress does anything but tell Tor to tell Windows to tell mIRC to never connect to the right place?
I'm sure I'm missing something obvious, just don't see what? And the whole "timing out" thing is what I'd expect when you try to connect to a black hole at an address that no one's listening at...?
-
Tor does the DNS resolving. Here's what I know about it (quoting from the Freenode web site):
=====
If your IRC client can handle socks5 with remote dns, you can just connect to the .onion address directly. Otherwise, use Tor's "mapaddress" feature to fake it. (We do not recommend that you use Privoxy with irssi. It's unnecessary. Just use the 'mapaddress' approach and torify irssi to start it up.) Add a line to your torrc, as in this example:
mapaddress 10.40.40.40 p4fsi4ockecnea7l.onion
Be sure to HUP (reload) Tor if you change your torrc. After you've made the change, just connect your torified IRC client to the IP you specified in your mapaddress statement for the freenode service. Tor will do the conversion for you internally and you'll connect to freenode.
=====
Note that this "remote DNS resolving" is a feature of Socks5. Apparently, if the IRC client is configured for Socks4 or Socks4a, it won't work. So that's one potential problem. If you are using the wrong Socks port (9150 in this case), that's another potential problem.
If your program can do Socks5 but not the "remote DNS resolving" part, that's a third potential problem. The fact that it said error resolving server is why I thought this was the problem and mapaddress is the solution. Even if it isn't the problem, using mapaddress won't hurt.
Now I'm not sure what the problem is, but they should check all the configuration stuff I mentioned again.
-
So i kept the bundle with the amended torrc file and reinstalled mIRC this time.
Did nothing to mIRC but:
1. Enter Nickname
2. Add new Server: silcroadg3c3mtu6.onion Ports: 6667
3. Enter Proxy: 127.0.0.1 Port: 9150 Protocol: Socks5
4. Connect
5. Change Server: 192.0.2.2 Ports: 6667
5. Connect
Result:
* Connect retry #3 silcroadg3c3mtu6.onion (6667)
-
* Unable to resolve server ------------ instantly
-
* Connect retry #4 silcroadg3c3mtu6.onion (6667)
-
* Unable to resolve server ------------ instantly
-
* Connect cancelled
-
* Connecting to 192.0.2.2 (6667)
-
* Unable to connect to server (Permission denied) ------------ instantly, this is where i had to allow it in firewall control
-
* Connect retry #1 192.0.2.2 (6667)
-
* Unable to connect to server (Connection timed out) ------------ ~25s delayed
-
* Connect retry #2 192.0.2.2 (6667)
-
* Unable to connect to server (Connection timed out) ------------ ~25s delayed
-
Repeated last one 12 times with changing identity in the Vidalia Control Panel 3 times.
-
Now THAT is how you ask for help. Nicely detailed. :)
So yeah with the 25 second delay I'd say you just can't connect to the server.
You can check to see if Tor is trying to connect to it. onion icon -> Network Map
Let your browser bundle sit idle for a few minutes so it isn't building circuits. Then try to connect in mIRC and you should see it building a lot of circuits (that fail). Then I'd say it is confirmed that your Tor is having trouble connecting to the hidden service (and mIRC is configured correctly).
-
Ahh, I got it. So yeah, I guess that would work -- mIRC sees the already-resolved address and calls for a socket to that address, which Windows fulfills and gives back to mIRC. What mIRC doesn't know though is that Tor has already mentioned to Windows that 192.0.2.2 is a synonym for 127.0.0.1, so Windows connected the socket mIRC asked for to 127.0.0.1:9150 and not 192.0.2.2/6667 like mIRC thought.
Then Tor does it's usual thing, all while mIRC is unaware it isn't connecting directly to whatever wherever. Neat. Seems like the same thing as torify or socksify does, basically, but still neat that Tor has the feature written in natively.
-
I see a lot of activity when i use the browser: open, connecting, closed
But when the page has loaded everything is on "open".
When i try to connect through mIRC nothing at all happens.
Edit: This was a result of astor's instructions.
-
I found this thread interesting so I decided to figure it out myself.
I am going to try the information found on this page http://kpvz7ki2v5agwt35.onion/wiki/index.php/OnionNet
They say mIRC isn't recommended.
I'm going to try the KVIrc instructions.
-
I see a lot of activity when i use the browser: open, connecting, closed
But when the page has loaded everything is on "open".
When i try to connect through mIRC nothing at all happens.
Edit: This was a result of astor's instructions.
Oh, that's bad. That means Tor isn't trying to reach the server. As Hash said, there could be some problem with mIRC. I was able to get mIRC to connect when I tested it in a Windows VM, but who knows.
You could try with Pidgin. Pidgin works well with Tor. It even has a Tor mode. Use all the same configuration settings except use the onion address for server, not the IP address. Remove the mapaddress line in torrc.
In the proxy settings, use Tor/Privacy (SOCKS5) instead of the SOCKS5 option.
-
I found this thread interesting so I decided to figure it out myself.
I am going to try the information found on this page http://kpvz7ki2v5agwt35.onion/wiki/index.php/OnionNet
They say mIRC isn't recommended.
I'm going to try the KVIrc instructions.
This works!
I can honestly tell you I have never used IRC before this date.
Get KVIrc and follow the instructions on that page.
You will be online in a few minutes if you read it.
-
You could try with Pidgin. Pidgin works well with Tor. It even has a Tor mode.
This is the way to go people!
mIRC=48h setup without success
Pidgin=2min and you are connected
Thx to astor, SS and hash!